Hi Russ,
Sounds like things are miss-configured, but you neglected to state how things are configured.
A common mistake is to confuse configuring IO numbers
instead of Device numbers. Reading this Thread may help even though it relates to DAC devices rather than Step/Dir Generators. http://www.cnczone.com/forums/dynomotion-kflop-kanalog/215344-anilam-supermax-frankenstein-project-using-dynomotion-kflop.html#post1457956
Step/Dir Generators with LVTTL outputs should work with Gecko G540's so you would configure Step/Dir Generator Channels as 8, 9, and 10. See also: http://www.dynomotion.com/Help/StepAndDirection/StepAndDir.htm
Do not run Mach3 until after you get the axes working.
HTH Regards TK
| Group: DynoMotion |
Message: 9484 |
From: Russ Larson |
Date: 5/10/2014 |
| Subject: Re: Mach3 Plugin Bug |
Tom, Here is a little more information, they we have collected over the last couple hours. Some additional information: Version 4.32 verified in Console screen. The digital I/O screen also agrees with what we are seeing. When first powering up the kflop we set CH 0 to I/O 8, CH1 to I/O 10, and CH2 to I/O 12. Then moving each of the channels one at a time the following is observed in the Digital I/O screen: * moving CH0 gets I/O 8 and I/O 9 bit and state checked * moving CH1 gets I/O 12 and I/O 13 bit and state checked (I expected I/O 10 and 11 to get checked, not CH2 I/O mapping) * moving CH2 gets I/O 36 and I/O 37 bit and state checked (I expected I/O 12 and 13 to get checked) Also went back to version 4.31 and repeated with the same results. Regards, Russ From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com]
Sent: Saturday, May 10, 2014 7:05 PM
To: DynoMotion@yahoogroups.com
Cc: 'Mark Vogel'
Subject: RE: [DynoMotion] Mach3 Plugin Bug Tom, We have been working on a KFLOP unit for a three axis stepper and we now have the optical homing sensors working great with the addition of the pull up resistor you suggested. We have tested the X axis and it moves just fine. Then we tested the Y axis and the Z axis moved, we figured we had two wires switched. Then we tested the Z axis and nothing moved. We carefully traced all the wires and in fact disconnected the KFLOP completely and hooked up the Gecko G540 directly to a laptop with MACH3. All three axis work perfect with no issues. So we know the motors and the Gecko G540 are all good. We then retraced all the wires again and in fact only hooked up the minimal set of wires, excluding all normal IO. We are using JP7-15,JP7-16 as Step0, Direction 0 **** This works :) We are using JP7-17, JP7-18 as Step1, Direction 1 **** This moves the Z axis We are using JP7-19,JP7-20 as Step2, Direction 2 **** This moves nothing We have spent hours working on this looking for mistakes, but this actually looks like the FPGA is getting configured wrong. We are using the latest version of Kmotion and the KFLOP has been flashed and it matches Kmotion when you go to the console and check version. Any thoughts? Thanks Russ Larson |
|
| Group: DynoMotion |
Message: 9485 |
From: Russ Larson |
Date: 5/10/2014 |
| Subject: Re: Mach3 Plugin Bug |
TK, We are using Output 8, for the first motor, Output 10 for the Y motor, and output 12 for the Z motor? I thought it had you use 8, and it automatically skipped one for direction and then 10.. sounds like you are suggesting 8,9,10 We are using LVTTL outputs and they are working with the Gecko. We are not running Mach3 at all, just in Kmotion testing so far. Russ From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com]
Sent: Saturday, May 10, 2014 8:42 PM
To: DynoMotion@yahoogroups.com
Subject: Re: [DynoMotion] Mach3 Plugin Bug Sounds like things are miss-configured, but you neglected to state how things are configured. A common mistake is to confuse configuring IO numbers instead of Device numbers. Reading this Thread may help even though it relates to DAC devices rather than Step/Dir Generators. Step/Dir Generators with LVTTL outputs should work with Gecko G540's so you would configure Step/Dir Generator Channels as 8, 9, and 10. See also: Do not run Mach3 until after you get the axes working. We have been working on a KFLOP unit for a three axis stepper and we now have the optical homing sensors working great with the addition of the pull up resistor you suggested. We have tested the X axis and it moves just fine. Then we tested the Y axis and the Z axis moved, we figured we had two wires switched. Then we tested the Z axis and nothing moved. We carefully traced all the wires and in fact disconnected the KFLOP completely and hooked up the Gecko G540 directly to a laptop with MACH3. All three axis work perfect with no issues. So we know the motors and the Gecko G540 are all good. We then retraced all the wires again and in fact only hooked up the minimal set of wires, excluding all normal IO. We are using JP7-15,JP7-16 as Step0, Direction 0 **** This works :) We are using JP7-17, JP7-18 as Step1, Direction 1 **** This moves the Z axis We are using JP7-19,JP7-20 as Step2, Direction 2 **** This moves nothing We have spent hours working on this looking for mistakes, but this actually looks like the FPGA is getting configured wrong. We are using the latest version of Kmotion and the KFLOP has been flashed and it matches Kmotion when you go to the console and check version. |
|
| Group: DynoMotion |
Message: 9486 |
From: Tom Kerekes |
Date: 5/10/2014 |
| Subject: Re: Mach3 Plugin Bug |
Hi Russ, Not sure if our emails crossed... But again - don't configure I/O numbers. Configure Step/Dir Generator Channels. Axis Chan0 - OutputChan0 = 8 (Step/Dir Generator #0 in LVTTL Mode)
Axis Chan1 - OutputChan0 = 9 (Step/Dir Generator #1 in LVTTL Mode)
Axis Chan2 - OutputChan0 = 10 (Step/Dir Generator #2 in LVTTL Mode)
HTH Regards TK
| Group: DynoMotion |
Message: 9487 |
From: Russ Larson |
Date: 5/10/2014 |
| Subject: Re: Mach3 Plugin Bug |
TK, Wow you are amazing. We did a quick check and output channel to 8,9,10. Wow, guess we were configuring IO numbers instead of device numbers. I have studied this documentation so many times I am still scratching my head. Reading the link you provided from cnczone now. Thanks again for the prompt response. I wish we had send you an email this morning and not spent the entire day pulling our hair out. LOL Thanks again Tom Russ From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com]
Sent: Saturday, May 10, 2014 8:42 PM
To: DynoMotion@yahoogroups.com
Subject: Re: [DynoMotion] Mach3 Plugin Bug Sounds like things are miss-configured, but you neglected to state how things are configured. A common mistake is to confuse configuring IO numbers instead of Device numbers. Reading this Thread may help even though it relates to DAC devices rather than Step/Dir Generators. Step/Dir Generators with LVTTL outputs should work with Gecko G540's so you would configure Step/Dir Generator Channels as 8, 9, and 10. See also: Do not run Mach3 until after you get the axes working. We have been working on a KFLOP unit for a three axis stepper and we now have the optical homing sensors working great with the addition of the pull up resistor you suggested. We have tested the X axis and it moves just fine. Then we tested the Y axis and the Z axis moved, we figured we had two wires switched. Then we tested the Z axis and nothing moved. We carefully traced all the wires and in fact disconnected the KFLOP completely and hooked up the Gecko G540 directly to a laptop with MACH3. All three axis work perfect with no issues. So we know the motors and the Gecko G540 are all good. We then retraced all the wires again and in fact only hooked up the minimal set of wires, excluding all normal IO. We are using JP7-15,JP7-16 as Step0, Direction 0 **** This works :) We are using JP7-17, JP7-18 as Step1, Direction 1 **** This moves the Z axis We are using JP7-19,JP7-20 as Step2, Direction 2 **** This moves nothing We have spent hours working on this looking for mistakes, but this actually looks like the FPGA is getting configured wrong. We are using the latest version of Kmotion and the KFLOP has been flashed and it matches Kmotion when you go to the console and check version. |
|
| Group: DynoMotion |
Message: 9488 |
From: Russ Larson |
Date: 5/10/2014 |
| Subject: Re: Mach3 Plugin Bug |
You were 100% correct and now after reading the exchange on cnczone, I have discovered what you pointed out. Lots of concepts on the KFLOP that I just misunderstood. The motors now all move correctly. You are AWESOME, thanks TK Next we will start working on the C programs... :) Russ From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com]
Sent: Saturday, May 10, 2014 8:56 PM
To: DynoMotion@yahoogroups.com
Subject: Re: [DynoMotion] Mach3 Plugin Bug Hi Russ,
Not sure if our emails crossed...
But again - don't configure I/O numbers. Configure Step/Dir Generator Channels.
Axis Chan0 - OutputChan0 = 8 (Step/Dir Generator #0 in LVTTL Mode)
Axis Chan1 - OutputChan0 = 9 (Step/Dir Generator #1 in LVTTL Mode)
Axis Chan2 - OutputChan0 = 10 (Step/Dir Generator #2 in LVTTL Mode)
Here is a little more information, they we have collected over the last couple hours. Some additional information: Version 4.32 verified in Console screen. The digital I/O screen also agrees with what we are seeing. When first powering up the kflop we set CH 0 to I/O 8, CH1 to I/O 10, and CH2 to I/O 12. Then moving each of the channels one at a time the following is observed in the Digital I/O screen: * moving CH0 gets I/O 8 and I/O 9 bit and state checked * moving CH1 gets I/O 12 and I/O 13 bit and state checked (I expected I/O 10 and 11 to get checked, not CH2 I/O mapping) * moving CH2 gets I/O 36 and I/O 37 bit and state checked (I expected I/O 12 and 13 to get checked) Also went back to version 4.31 and repeated with the same results. We have been working on a KFLOP unit for a three axis stepper and we now have the optical homing sensors working great with the addition of the pull up resistor you suggested. We have tested the X axis and it moves just fine. Then we tested the Y axis and the Z axis moved, we figured we had two wires switched. Then we tested the Z axis and nothing moved. We carefully traced all the wires and in fact disconnected the KFLOP completely and hooked up the Gecko G540 directly to a laptop with MACH3. All three axis work perfect with no issues. So we know the motors and the Gecko G540 are all good. We then retraced all the wires again and in fact only hooked up the minimal set of wires, excluding all normal IO. We are using JP7-15,JP7-16 as Step0, Direction 0 **** This works :) We are using JP7-17, JP7-18 as Step1, Direction 1 **** This moves the Z axis We are using JP7-19,JP7-20 as Step2, Direction 2 **** This moves nothing We have spent hours working on this looking for mistakes, but this actually looks like the FPGA is getting configured wrong. We are using the latest version of Kmotion and the KFLOP has been flashed and it matches Kmotion when you go to the console and check version. |
|
| Group: DynoMotion |
Message: 9489 |
From: Tom Kerekes |
Date: 5/10/2014 |
| Subject: Re: Mach3 Plugin Bug |
Hi Russ, Sorry it is so confusing. I guess it doesn't help that Step/Dir Generator Channel #8 just coincidentally happens to be connected to IO #8 (and #9) to make matters more confusing. Regards TK
| Group: DynoMotion |
Message: 9491 |
From: Russ Larson |
Date: 5/11/2014 |
| Subject: Re: Mach3 Plugin Bug |
TK, You are correct that is the trap I fell into. LOL At least you bailed me out. Thanks Again Russ From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com]
Sent: Saturday, May 10, 2014 9:21 PM
To: DynoMotion@yahoogroups.com
Subject: Re: [DynoMotion] Mach3 Plugin Bug Hi Russ,
Sorry it is so confusing. I guess it doesn't help that Step/Dir Generator Channel #8 just coincidentally happens to be connected to IO #8 (and #9) to make matters more confusing.
Regards
TK Wow you are amazing. We did a quick check and output channel to 8,9,10. Wow, guess we were configuring IO numbers instead of device numbers. I have studied this documentation so many times I am still scratching my head. Reading the link you provided from cnczone now. Thanks again for the prompt response. I wish we had send you an email this morning and not spent the entire day pulling our hair out. LOL Thanks again Tom Sounds like things are miss-configured, but you neglected to state how things are configured. A common mistake is to confuse configuring IO numbers instead of Device numbers. Reading this Thread may help even though it relates to DAC devices rather than Step/Dir Generators. Step/Dir Generators with LVTTL outputs should work with Gecko G540's so you would configure Step/Dir Generator Channels as 8, 9, and 10. See also: Do not run Mach3 until after you get the axes working. We have been working on a KFLOP unit for a three axis stepper and we now have the optical homing sensors working great with the addition of the pull up resistor you suggested. We have tested the X axis and it moves just fine. Then we tested the Y axis and the Z axis moved, we figured we had two wires switched. Then we tested the Z axis and nothing moved. We carefully traced all the wires and in fact disconnected the KFLOP completely and hooked up the Gecko G540 directly to a laptop with MACH3. All three axis work perfect with no issues. So we know the motors and the Gecko G540 are all good. We then retraced all the wires again and in fact only hooked up the minimal set of wires, excluding all normal IO. We are using JP7-15,JP7-16 as Step0, Direction 0 **** This works :) We are using JP7-17, JP7-18 as Step1, Direction 1 **** This moves the Z axis We are using JP7-19,JP7-20 as Step2, Direction 2 **** This moves nothing We have spent hours working on this looking for mistakes, but this actually looks like the FPGA is getting configured wrong. We are using the latest version of Kmotion and the KFLOP has been flashed and it matches Kmotion when you go to the console and check version. |
|
| | | | | |
